System and method for intelligently interfacing with financial information

ABSTRACT

A system and method for interfacing with financial information. The system includes a touch screen display. The touch-screen display includes a plurality of logical regions. Each one of the plurality of logical regions includes content that is expandable based on a user selection. The system also includes logic to associate a plurality of a user&#39;s financial data of a predetermined type with each one of the logical regions. The system further includes logic to vary an amount of the associated financial data displayed on the display based on a first type of user selection of one of the logical regions.

BACKGROUND

Interfacing with financial information, and initiating transactions withfinancial information, over the Internet has increased exponentiallyover the past few years. Financial services provided at brick and mortarbanking facilities is becoming more and more obsolete. Mobile devicessuch as cellular phones, Personal Digital Assistants (PDAs), tablets,and other wirelessly enabled devices have successfully penetrated andbeen adopted by the general consumer market. Individuals have come toenjoy the convenience, flexibility and mobility of wireless devices as ameans to facilitate communications and interact with friends, family,colleagues and business entities.

In the case of Internet-based information interfaces, and initiatingtransactions over the Internet, conventional hierarchical navigationinterfaces can be cumbersome and require a certain degree of learningand experience development on the part of a user of such an interface.Conventional hierarchical menu-based navigational interfaces wereintroduced to computers as a method of organizing data, such asmainframe data upon which the interface was based. A conventionalservice provider web site can include a login page, then after asuccessful login, a user is directed to a web page showing a list ofavailable services. To move from a login screen, to a service browsingscreen, or a transaction screen, requires passing through several webpages. If a service is selected, the webpage reloads with details. Toswitch to a different service, the user must go back through a series ofpages that they previously navigated, or in some cases, jump back to aservice provider list from a drop-down menu and navigate to a desiredservice. These conventional methods can be cumbersome and can provide auser with a non-intuitive user interface.

Thus, there remains a need to overcome conventional limitations andprovide a system and method to intelligently interface with information,including financial information, and execute financial transactionrequests, over the Internet.

SUMMARY

The present disclosure is directed generally to systems and methods forintelligently interfacing with financial information. One embodiment ofthe present subject matter provides a system of interfacing withfinancial information including a touch-screen display. The touch screendisplay can include a plurality of logical regions. Each one of theplurality of logical regions includes content that is expandable basedon a user selection. The system can include logic to associate aplurality of a user's financial data of a predetermined type with eachone of the logical regions. The system can also include logic to vary anamount of the associated financial data displayed on the display basedon a first type of user selection of one of the logical regions.

Another embodiment of the present subject matter provides a system ofinterfacing with financial information including a touch-screen display.The touch screen display can include a plurality of logical regions.Each one of the plurality of logical regions includes content that isexpandable based on a user selection. The system can include a computerprocessor having a computer readable storage medium. The computerreadable storage medium can include instructions stored therein forexecuting on the computer processor. The instructions when read andexecuted on the computer processor can cause the computer processor toassociate a plurality of a user's financial data of a predetermined typewith each one of the logical regions and to vary an amount of theassociated financial data displayed on the display based on a first typeof user selection of one of the logical regions.

Another embodiment of the present subject matter provides a method ofexecuting a financial transaction request. The method can includeassociating a plurality of a user's financial data of a firstpredetermined type with a first logical region on a touch screen displayand associating a plurality of a user's financial data of a secondpredetermined type with a second logical region on the touch screendisplay. The method can also include receiving a user selection of atleast a portion of the user's financial data in each of the first andsecond logical regions. The at least a portion of the user's financialdata of the first logical region can be associated with the at least aportion of the user's financial data of the second logical region basedon the received user selection. A financial transaction can be initiatedbased on the received user selection and using the associated respectiveportions of the user's financial data of the first and second logicalregions.

Another embodiment of the present subject matter provides a system ofexecuting a financial request including a touch-screen display. Thetouch screen display can include a plurality of logical regions. Eachone of the plurality of logical regions can include content that isexpandable based on a user selection. The system can include a computerprocessor having a computer readable storage medium. The computerreadable storage medium can include instructions stored therein forexecuting on the computer processor. The instructions when read andexecuted on the computer processor can cause the computer processor toassociate a plurality of a user's financial data of a firstpredetermined type with a first logical region on the touch screendisplay and associate a plurality of a user's financial data of a secondpredetermined type with a second logical region on the touch screendisplay. The instructions when read and executed on the computerprocessor can also cause the computer processor to receive a userselection of at least a portion of the user's financial data in each ofthe first and second logical regions, associate the at least a portionof the user's financial data of the first logical region with the atleast a portion of the user's financial data of the second logicalregion based on the received user selection and initiate a financialtransaction based on the received user selection and using theassociated respective portions of the user's financial data of the firstand second logical regions.

A further embodiment of the present subject matter provides a method ofexecuting a financial transaction request. The method can includeassociating a plurality of a user's financial data of a firstpredetermined type with a first logical region on a touch screen displayand associating a plurality of a user's financial data of a secondpredetermined type with a second logical region on the touch screendisplay. The method can also include associating a first subset of thedata of the first predetermined type with a first logical subregion inthe first logical region and associating a second subset of the data ofthe first predetermined type with a second logical subregion in thefirst logical region. A user selection of at least a portion of the datain each of the first and second logical subregions can be received. Themethod can include associating the at least a portion of the data of thefirst logical subregion with the at least a portion of the data of thesecond logical subregion based on the received user selection. Afinancial transaction can be initiated based on the received userselection and using the associated respective portions of the data ofthe first and second logical subregions.

An additional embodiment of the present subject matter provides a systemof executing a financial request including a touch-screen display. Thetouch screen display can include a plurality of logical regions. Eachone of the plurality of logical regions can include content that isexpandable based on a user selection. A first logical region can includea plurality of logical subregions. Each one of the logical subregionscan include content that is expandable based on a user selection. Thesystem can include a computer processor having a computer readablestorage medium. The computer readable storage medium can includeinstructions stored therein for executing on the computer processor. Theinstructions when read and executed on the computer processor can causethe computer processor to associate a plurality of a user's financialdata of a first predetermined type with a first logical region on thetouch screen display and associate a plurality of a user's financialdata of a second predetermined type with a second logical region on thetouch screen display. The instructions when read and executed on thecomputer processor can also cause the computer processor to associate afirst subset of the data of the first predetermined type with a firstlogical subregion in the first logical region and associate a secondsubset of the data of the first predetermined type with a second logicalsubregion in the first logical region. The instructions when read andexecuted on the computer processor can also cause the computer processorto receive a user selection of at least a portion of the data in each ofthe first and second logical subregions, to associate the at least aportion of the data of the first logical subregion with the at least aportion of the data of the second logical subregion based on thereceived user selection, and to initiate a financial transaction basedon the received user selection and using the associated respectiveportions of the data of the first and second logical subregions.

These embodiments and many other objects and advantages thereof will bereadily apparent to one skilled in the art to which the inventionpertains from a perusal of the claims, the appended drawings, and thefollowing detailed description of the embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

Various aspects of the present disclosure will be or become apparent toone with skill in the art by reference to the following detaileddescription when considered in connection with the accompanyingexemplary non-limiting embodiments.

FIG. 1 is an illustration of a wireless banking system connected to aplurality of devices according to some embodiments of the presentdisclosure.

FIG. 2 is an illustration of an architecture of a computer processingunit according to some embodiments of the present disclosure.

FIGS. 3A-3F are illustrative screenshots according to some embodimentsof the present subject matter.

FIG. 4 is a simplified block diagram of one embodiment of the presentsubject matter.

FIGS. 5A-5B are illustrative screenshots according to some embodimentsof the present disclosure.

FIG. 6 is a simplified block diagram of one embodiment of the presentsubject matter.

FIG. 7 is a simplified block diagram of another embodiment of thepresent subject matter.

FIGS. 8A-8B are illustrative screenshots according to some embodimentsof the present disclosure.

FIG. 9 is a simplified block diagram of an embodiment of the presentdisclosure.

FIG. 10 is a simplified block diagram of an embodiment of the presentdisclosure.

FIGS. 11A-11B are illustrative screenshots according to some embodimentsof the present subject matter.

FIG. 12 is a block diagram of a processing system according to anembodiment of the present disclosure.

DETAILED DESCRIPTION

With reference to the figures where like elements have been given likenumerical designations to facilitate an understanding of the presentsubject matter, the various embodiments of a system and method forinterfacing with financial information are provided.

As more consumers interface with their financial information over theInternet, and switch to mobile devices (e.g. smart phones, tablets) astheir primary means of interacting with the Internet, it is increasinglyimportant for financial institutions or entities to have the ability tointelligently interface with user financial information on these mobiledevices. Embodiments of the present subject matter can be utilized toprovide a user or individual (e.g. a financial institution customer)with the ability to intelligently interface with an entity or custodian(e.g. financial institution) and their user financial information thatis also associated with such an entity or custodian. In someembodiments, a custodian can be, for example, a financial institutionsuch as a bank, brokerage firm or other similar entity. Of course, acustodian may also be any agent or any agent's computer or computersacting as an intermediary between two other parties or computers of twoother parties where access, such as via the Internet, to certaininformation or data is designed to be limited, regardless of whether ornot the information or data is confidential. A custodian may alsoinclude a secure operating system executing on a microprocessor-basedcomputer terminal or device capable of interactive networkcommunications, or wireless device that connects to, and communicatesthrough, the Internet using, for example, a wireless access protocol(WAP) or other protocol, and utilizing operating-system controls tolimit access to data.

FIG. 1 is an illustration of a wireless banking system 100 connected toa plurality of devices 110, 111, 112. The wireless banking system 100may be employed by a custodian described above or any agent orintermediary thereof, for example. An wireless banking system 100 may beselectively coupled to a plurality of devices through the Internet 114or another known means. Exemplary devices may be desktop or laptopcomputers 110, tablets 111, mobile devices 112 such as cell phones,smart phones, and the like. Each of the devices 110, 111, 112 may havevarious devices connected to, or included with, their local computersystems, such as scanners, cameras, webcams, barcode readers, printers,finger print scanners, mouse devices, keyboards, and other interfacedevices. In some embodiments, each of the devices 110, 111, 112 has atouch screen interface. The wireless banking system 100 may be protectedfrom network attacks by a piece of software or specialized hardware,commonly known as a firewall. It is understood that a firewall may beused to block network connections from the outside world to the bankingsystems 100 inside the firewall. It is also understood that firewallsare often governed by a set of rules that specify what IP addresses,ports, and even types of traffic are allowed to connect to machinesinside the firewall. It is also understood that other network securitydefense tools may be employed as part of a defense-in-depth strategy tosecure the wireless banking system 100 including, but not limited to,intranet subnet partitioning, intrusion detection or host-basedintrusion prevention systems. Communications between any or all of thedevices to an exemplary wireless banking system 100 may be via atransport layer security (TLS) tunnel or secure sockets layer (SSL)tunnel, virtual private network (VPN) connection, etc. to preventsnooping and/or alteration of such communications and respectiveinformation. These tunnels are exemplary only as other cryptographicprotocols may be employed to provide communications security over theInternet.

An exemplary wireless banking system 100 may include a processing unit102 coupled to one or more data storage units 104, 106. The processingunit 102 may provide front-end graphical user interfaces (GUI), e.g.,customer GUI 108 and a service provider GUI 109, as well as back-endGUIs 107 to a device 110, 111, 112 or to a local computer 116. The GUIsmay take the form of, for example, a webpage that is displayed using abrowser program local to the device 110, 111, 112 or to the localcomputer 116. It is understood that the wireless banking system 100 maybe implemented on one or more computers 116, servers 118, or likedevices. For example, a wireless banking system 100 may include serversprogrammed or partitioned based on permitted access to the data of acustodian or customer and may include communications servers tofacilitate communications between the devices 110, 111, 112 and thesystem 100. It should be noted that the terms “consumer,” “customer,”“individual” and “user” are used interchangeably herein and such useshould not limit the scope of the claims appended herewith. Front- andback-end GUIs 107, 108, 109 may be portal pages that include variouscontent retrieved from the one or more data storage devices 104, 106. Asused herein, “portal” may be general-purpose Internet portals and/or mayinclude GUIs that are of interest to specific, limited audiences andthat provide a user access to a plurality of different kinds of relatedor unrelated information, links and tools as described below. It shouldalso be noted that the terms “webpage” and “website” may be usedinterchangeably herein and such use should not limit the scope of theclaims appended herewith.

A user or customer may gain access to the wireless banking system 100 byusing a device 110, 111, 112, 116, programmed with a Web browser orother software, to locate and select (such as by touching a screen ofthe device) a particular webpage. Application Programming Interfaces(APIs) may be employed to provide connectivity between applicationsresident on the devices 110, 111, 112, 116 and underlying data in thesystem 100 or services provided by an entity, custodian or institution.In exemplary embodiments, a device 110, 111, 112, 116 can support anadvanced markup language (e.g. HTML5). In some embodiments, webpagecontent can be created by client-side scripting. In some embodiments, awebpage is a dynamic webpage. In some embodiments, webpage content canbe created by server-side scripting such as, for example, PHP, Perl,JSP, ASP.NET, etc. In some embodiments, dynamic HTML (DHTML) can be usedto create webpage content including, for example, a combination of astatic markup language (e.g. HTML), a client-side scripting language(e.g. JavaScript), a presentation definition language (e.g. CSS), theDocument Object Model, etc.

The content of the webpage may be located on the one or more datastorage devices 104, 106. The device 110, 111, 112, 116 may be amicroprocessor-based computer terminal, a pager adaptable to communicatethrough the Internet, Kiosks with Internet access, personal digitalassistants (PDAs) (e.g., a PALM device manufactured by Palm, Inc., IPAQdevice available from Compaq, iPhone from Apple or BLACKBERRY from RIM),cellular phone, tablet (e.g. iPad manufactured by Apple, or Nookmanufactured by Barnes and Noble, Kindle manufactured by Amazon, Nexusmanufactured by Google, Galaxy manufactured by Samsung, etc.), slatetablet, booklet computer, convertible notebook, phablet (e.g. LG OptimusVu, Samsung Galaxy Note, Dell Streak, etc.) or other devices capable ofinteractive network communications, such as an electronic personalplanner. Of course, such devices 110, 111, 112, 116 may be wireless orwire-line that connect to and communicate through the Internet. Asmentioned above, an exemplary wireless banking system 100 may provideseparate features and functionality for users thereof, includingcustomers and service providers, as well as back-end users that managethe wireless banking system 100.

FIG. 2 is an illustration of an architecture of a computer processingunit 102 configured to implement the algorithms and software programmingassociated with the present disclosure. This unit may be a standaloneunit or portion thereof. This unit may include a device processor, aserver processor, or combination thereof. As illustrated in FIG. 2, thecomputer processor unit 102 may include one or more processors 202. Theprocessor 202 may be connected to a communication infrastructure 206(e.g., a communications bus, cross-over bar, server or network). Asdiscussed above, the computer processing unit 102 may include a displayinterface that forwards graphics, text, and other data from thecommunication infrastructure (or from a frame buffer not shown) fordisplay on the front- and back-end GUIs 107, 108, 109 and as retrievedfrom the one or more data storage devices 104, 106.

The computer processing unit 102 may also include a main memory 204,such as a random access memory (RAM), and a secondary memory 208. Thesecondary memory 208 may include, for example, a hard disk drive (HDD)210 and/or removable storage drive 212, which may represent a floppydisk drive, a magnetic tape drive, an optical disk drive, or the like.The removable storage drive 212 may read from and/or write to aremovable storage unit 216. The removable storage unit 216 may be afloppy disk, magnetic tape, optical disk, or the like. As will beunderstood, the removable storage unit 216 may include a computerreadable storage medium having stored therein computer software and/ordata.

In alternative embodiments, the secondary memory 208 may include othersimilar devices for allowing computer programs or other instructions tobe loaded into the computer processing unit 102. The secondary memory208 may include a removable storage unit 218 and a correspondinginterface 214. Examples of such removable storage units include, but arenot limited to, USB or flash drives, which allow software and data to betransferred from the removable storage unit 218 to the computerprocessing unit 102.

The computer processing unit 102 may also include a communicationsinterface 220 allowing software and data to be transferred betweencomputer processing unit 102 and external devices. Examples of acommunications interface 220 may include a modem, Ethernet card,wireless network card, a Personal Computer Memory Card InternationalAssociation (PCMCIA) slot and card, or the like. Software and datatransferred via the communications interface 220 may be in the form ofsignals, which may be electronic, electromagnetic, optical, or the likethat are capable of being received by the communications interface 220.These signals may be provided to the communications interface 220 via acommunications path (e.g., channel), which may be implemented usingwire, cable, fiber optics, a telephone line, a cellular link, a radiofrequency (RF) link and other communication channels.

The terms “computer program medium” and “computer readable storagemedium” may generally refer to media such as a removable storage drive212, a hard disk installed in a hard disk drive 210, a non-transitorycomputer readable storage medium, etc. These computer program productsmay provide software to computer processing unit 102. Computer programs(also referred to as computer control logic) may also be stored in themain memory 204, secondary memory 208 and/or data storage devices 104,106. Computer programs may also be received via the communicationsinterface 220. Such computer programs, when executed by a processor,specifically enable the computer processing unit 102 to perform featuresof the methods discussed herein. In an embodiment implemented usingsoftware, the software may be stored in a computer program product andloaded into computer processing unit 102 using a removable storage drive212, hard drive 210, or communications interface 220. The software, whenexecuted by a processor 202, causes the processor 202 to specificallyperform the functions described herein.

As customer interactions with entities such as financial institutionscontinue to shift toward Internet-based interactions, entities providingefficient, intelligent interfaces that improve a user's experience havesignificant advantages over other institutions. For example, capable,intelligent interfaces may be employed to improve the experience of auser or individual of a hierarchical (e.g. menu-driven) personalcomputer interface by minimizing, and efficiently using, user dataentry.

One embodiment of the present subject matter may allow an individual toaccess a banking system utilizing a mobile device 110, 111, 112 such as,but not limited to, a laptop computer, tablet, cell phone, smart phone,and the like. Of course, these devices may include applicable operatingsystems thereon (e.g., iOS, Android, Windows, etc.). In otherembodiments, a banking system can be accessed using a personal computersuch as, for example, a desktop computer. As discussed above, exemplarydevices can include a touch screen display for intelligently interfacingwith a financial information and with a respective institution. A touchscreen display can be of any suitable form and technology including, butnot limited to, a cathode-ray tube display, a liquid crystal display, aresistive touch screen display, a capacitive touch screen display, amulti-touch capable touch screen display, etc.

By the way of a non-limiting example, an iPhone or iPad (or otherdevice) user may download an application from a third party or aninstitution for the purpose of interfacing with their financialinformation, or in the alternative, may visit a website of theinstitution or third party. The institution or third party can providethe user with an intelligent banking interface to improve a user'sexperience through the graphical user interface of the device. Theinventor has observed that hierarchical (e.g. menu-driven) interfacesprovide various challenges to users especially users that frequentlytravel and have limited time to handle personal matters such as bankingor shopping. The inventor has determined that an intelligent interfacethat minimizes navigational and hierarchical user interactions with anapplication or website can significantly improve a user's experience ininteracting with their financial information and performing a widevariety of interactions and transactions with such financialinformation. The inventor has determined that providing an intelligent,user-friendly interface is significantly attractive to new and existingcustomers of a wide variety of Internet-based service providers.

Referring now to FIGS. 3A-3G, illustrative screenshots according to someembodiments of the present subject matter are provided. At FIG. 3A,portions of a system for interfacing with financial informationaccording to some embodiments are illustrated. As shown in FIG. 3A, atouch-screen display 305 is provided. In the illustrated embodiment, adevice 300 including the touch screen display 305 is provided. Asdescribed above, device 300 can include any suitable device such as, forexample, a microprocessor-based computer terminal, a mobile device, akiosk, a personal digital assistant, a cellular phone, a tablet, anelectronic personal planner, a slate tablet, a booklet computer, aconvertible notebook, a phablet, a smart phone, etc. Touch-screendisplay 305 can be any suitable touch screen display. For example, touchscreen display can be a cathode ray tube (CRT) touch screen display, aliquid crystal touch screen display (LCD), a LCD resistive touch screendisplay, a LCD capacitive touch screen display, a LCD multi-touchcapable touch screen display, etc.

In some embodiments, touch screen display 305 includes a plurality oflogical regions (310, 320, 330). As shown in the embodiments illustratedat FIGS. 3A-3F, each one of the plurality of logical regions (310, 320,330) can have content that is expandable based on a user selection. Forexample, as shown in FIG. 3A, logical region 310 includes displayedcontent of “Accounts”, logical region 320 includes displayed content of“Past Transactions”, and logical region 330 includes displayed contentof “Future Transactions”. In some embodiments, a system including touchscreen display 305 further includes logic to associate a plurality of auser's financial data of a predetermined type with each one of thelogical regions. The logic to associate may be implemented in anysuitable form, including, but not limited to, digital electroniccircuitry, computer software, firmware, or hardware, and including, forexample, as one or more computer program products (e.g. a computerreadable storage medium). In the embodiment illustrated in FIGS. 3A-3F,a system includes logic to associate a plurality of a user's accountdata with logical region 310. For example, a plurality of dataassociated with one or more user accounts (e.g. a checking account, ageneral services account, a savings account, a mortgage account, acredit card account, an investment account a retirement account, etc.)can be associated with logical region 310. A system can also includelogic to associate a plurality of a user's past transactional data withlogical region 320. For example, as shown in FIGS. 3A-3F, a plurality ofdata associated with a user's past or completed transactions (e.g. billspaid, purchases made, sales, money transferred, investments made, etc.)can be associated with logical region 320. In some embodiments, a systemcan also include logic to associate a plurality of a user's futuretransactions (e.g. a bill from a payee, a stock, an exchange-tradedfund, a money transfer, a deposit, a mortgage, an order, a scheduledpayment, a savings plan, an investment plan, etc.) with logical region330.

In some embodiments, a system can include logic to vary an amount of theassociated financial data displayed on the display 305 based on a typeof user selection of one of the logical regions (310, 320, 330). Thelogic to vary can be implemented in any suitable form. In the embodimentillustrated at FIGS. 3A-3F, a user can interact with the interface toobtain more detailed content associated with one or more of the logicalregions (310, 320, 330). A user interaction to select one or more of thelogical regions may be any suitable form of user selection (e.g. openpinch, closed pinch, tap, swipe, double click, keyboard stroke, etc.) Insome embodiments, one or more logical regions (310, 320, 330) areexpandable. The inventor has determined that an intelligent interface inwhich a user selection mechanism is associated with an intuitiveresponse from the display 305 can significantly improve a user'sexperience in interacting with their financial information andperforming a wide variety of interactions and transactions with suchfinancial information. For example, a user can interact with a logicalregion using an open pinch type of user selection and the logic to varycan respond by displaying on the display 305 a greater amount of theassociated financial data for that logical region (310, 320, 330).

In some embodiments, logic to vary can include logic to display detailedfinancial data of the predetermined type of the associated logicalregion based on an open pinch type of user selection of the logicalregion (310, 320, 330). As shown in FIGS. 3A and 3B, logic to vary canbe configured to display information associated with several useraccounts based on an open pinch type of user selection of logical region310. Referring now to FIGS. 3B and 3E, logic to vary can be configuredto display a greater amount (e.g. more detailed) account information fora particular account based on an open pinch or tap type of userselection of logical region 310. In the illustrated embodiment, a systemcan include a plurality of logical subregions (312, 314, 316) in atleast one of the plurality of logical regions (310, 320, 330). In someembodiments, each one of the plurality of logical subregions (312, 314,316) can include content that is expandable based on a user selection.In some embodiments, a system can include logic to associate a pluralityof the user's financial data of a predetermined type with each one ofthe logical subregions. For example, and as shown in FIG. 3B, the systemcan include logic to associate a plurality of data of a user's checkingaccount with logical subregion 312; a plurality of data of a user'ssavings account with logical subregion 314, and a plurality of data of auser's credit card account with logical subregion 316. In someembodiments, a system can include logic to associate information of auser's account with one of the logical subregions (312, 314, 316) andlogic to associate information of another one of the user's accountswith another one of the logical subregions (312, 314, 316). In someembodiments, one account of the user can be an account at one entity(e.g. bank, mortgage company, brokerage, etc.) and the other account ofthe user can be an account at another entity. In some embodiments, oneaccount of the user can be a checking account at one entity (e.g. bank,mortgage company, brokerage, etc.) and the other account of the user canbe a credit card account at the same entity. In some embodiments, one ormore logical subregions (312, 322, 332) are expandable.

Referring now to FIGS. 3B-3F, a system can include logic to vary anamount of a user's associated financial data displayed on display 305based on a type of user selection of one of the logical subregions (312,314, 316). The logic to vary can be implemented in any suitable form.For example, and as shown in the illustrated embodiments, logic to varycan include logic to display a greater amount (e.g. more detailed)account information for a particular account (e.g. checking account)based on a type of user selection (e.g. open pinch, tap, click, etc.) ofthe logical subregion (312, 314, 316). By way of example, and as shownin FIGS. 3B-3F, logic to vary can include logic to display a lesseramount (e.g. less detailed, more limited) account information for aparticular account (e.g. checking account) based on a type of userselection (e.g. closed pinch, second tap, second click, etc.) of thelogical subregion (312, 314, 316).

In some embodiments, logic to vary can include logic to display limitedfinancial data of the predetermined type based on another type of userselection. (e.g. closed pinch, tap, etc.) In the illustrated embodiment,logic to vary can be configured to display only the title “Accounts”based on another type of user selection (e.g. closed pinch or tap) oflogical region 310. Referring back to FIGS. 3A-3F, logic to vary can beconfigured to display on the display 305 a greater amount of (e.g. moredetailed) past transactional data (e.g. type of transaction (paid bills,grocery purchases, money transfers), an amount of the transaction, adate of the transaction, etc.) based on a type of user selection (e.g.open pinch, tap, click, etc.) of logical region 320, and/or a subregion(322, 324, 326, 328) of logical region 320, and a lesser amount of (e.g.less detailed, more limited) past transactional data based on anothertype of user selection (e.g. closed pinch, second tap, second click,double tap, double click, etc.) of logical region 320. Additionally, byway of example, logic to vary can be configured to display on thedisplay 305 a greater amount of (e.g. more detailed) futuretransactional data (e.g. type of future transaction (e.g. bills to bepaid, a stock scheduled for purchase, an exchange-traded fund scheduledfor order, a scheduled money transfer, a scheduled deposit, a scheduledmortgage payment, an order, a scheduled credit card payment, a savingsplan contribution, an investment plan contribution, etc.), an amount duefor the transaction, a date scheduled for the transaction, etc.) basedon a type of user selection (e.g. open pinch, tap, click, etc.) oflogical region 330, and/or a subregion (332, 334, 336) of logical region330, and a lesser amount of (e.g. less detailed, more limited) futuretransactional data based on another type of user selection (e.g. closedpinch, second tap, second click, double tap, double click, etc.) oflogical region 330.

In the illustrated embodiments of 3E and 3F, logic to vary can beconfigured to display on the display 305 a greater amount of (e.g. moredetailed) past transactional data for a particular transaction (e.g.bill payee, customer account number with payee, payee address, an amountof the transaction, a date of the transaction, etc. as shown in FIG. 3E)based on a type of user selection (e.g. open pinch, tap, click, etc.) oflogical region 320, or a subregion (322, 324, 326, 328) of logicalregion 320, and a lesser amount of (e.g. less detailed, more limited)past transactional data (e.g. a listing of past transactions includingbrief identity of payee, date of transaction, amount of transaction,etc. as shown in FIG. 3F) based on another type of user selection (e.g.closed pinch, second tap, second click, double tap, double click, etc.)of logical region 320, or a subregion of logical region 320.Additionally, by way of example, logic to vary can be configured todisplay on the display 305 a greater amount of (e.g. more detailed)future transactional data (e.g. bill payee, customer account number withpayee, payee address, an amount due for the transaction, a datescheduled for the transaction, etc., as shown in FIG. 3E) based on atype of user selection (e.g. open pinch, tap, click, etc.) of logicalregion 330, or a subregion (332, 334, 336) of logical region 330, and alesser amount of (e.g. less detailed, more limited) future transactionaldata (e.g. a listing of future transactions including brief identity ofpayee, date of transaction, amount of transaction, etc., as shown inFIG. 3F) based on another type of user selection (e.g. closed pinch,second tap, second click, double tap, double click, etc.) of logicalregion 330, or a logical subregion (332, 334, 336) of logical region330.

As shown in the embodiments of FIGS. 3C and 3D, a system can includelogic to vary the user's financial data displayed in at least one of thelogical regions (310, 320, 330) based on another type user selection.For example, display 305 can include one or more spin boxes (340, 350,360), or spinners, or scrolls, having an up arrow or a down arrow, toprovide the user with an interface to make another type of userselection of a logical region (310, 320, 330). In the illustratedembodiment, a type of user selection can be a selection of an up or downarrow of a spin box (340, 350, 360) associated with a logical region(310, 320, 330). In another embodiment (not shown), a type of userselection can be a selection of a scroll (not shown) associated with alogical region (310, 320, 330). In some embodiments, a system caninclude logic to vary the user's financial data displayed in at leastone of the logical regions (310, 320, 330) based on a user's selectionof an up or down arrow of s spin box 340 (or a selection of a scroll)associated with a logical region (310, 320, 330). For example, logic tovary can be configured to display on the display 305 different accountdata (e.g. mortgage account data, investment account data) based on auser's selection of an up arrow of a spin box 340 associated withlogical region 310 and/or less recent past transactional data (e.g. lessrecent bills paid, less recent transfers made, less recent purchasemade, etc.) based on a user's selection of a down arrow of a spin box350 associated with logical region 320. By way of example, logic to varycan be configured to display on the display 305 closer-in-time, orhigher priority, future transactional data (e.g. bills scheduled to paidat a chronologically higher order, scheduled transfers of a higheramount, investments scheduled to be made closer in time to when the userselection is made, etc.) based on a user's selection of an up arrow of aspin box 340 associated with logical region 330.

Referring now to the embodiment shown in FIG. 3D, a display 305 caninclude one or more swipe bars (345, 355, 365), having a right and leftswipe bar to provide the user with an interface to make another type ofuser selection of a logical region (310, 320, 330). For example, a typeof user selection can be a selection of a left or right swipe bar (345,355, 365) associated with a logical region (310, 320, 330). In someembodiments, a system can include logic to vary the user's financialdata displayed in at least one of the logical regions (310, 320, 330)based on a user's selection of a left or right swipe bar (345, 355, 365)associated with a logical region (310, 320, 330). For example, logic tovary can be configured to display on the display 305 different accountdata (e.g. mortgage account data, investment account data, etc.) basedon a user's right swipe of swipe bar 345 associated with logical region310 and/or different past transactional data (e.g. account debited from,time of transaction, balance remaining after transaction, etc.) based ona user's right swipe of swipe bar 355 associated with logical region320. By way of example, logic to vary can be configured to display onthe display 305 closer-in-time, or higher priority, future transactionaldata (e.g. bills scheduled to paid at a chronologically higher order,scheduled transfers of a higher amount, investments scheduled to be madecloser in time to when the user selection is made, etc.) based on auser's selection of an up arrow of a spin box 340 associated withlogical region 330.

In some embodiments, a display 305 can include one or more inlineimages, tags or logical regions, that are associated with user data of apredetermined type (e.g. financial data of the user at a separate entitythan an entity hosting or providing content to the website or appselected by the user, user data associated with a user account at amedia downloading site (e.g. iTunes account, Netflix account), user dataassociated with a user account at a social media site (e.g. Facebookaccount, Twitter account, LinkedIn account, Myspace account, user dataassociated with a user account at an online shopping or retailer site(e.g. Amazon.com, Best Buy, Barnes and Noble, eBay) etc.) In someembodiments, a user may initiate a request to link to such data by apredetermined type of user selection (e.g. click, tap, open pinch) ofthe inline image, tag, or logical region on touch screen display 305.

Referring now to FIG. 4, a simplified diagram showing a method ofexecuting a transaction request according to some embodiments isprovided. At block 410, a plurality of a user's financial data of apredetermined type is associated with a logical region (e.g. 310) on atouch screen display 305. At block 420, a plurality of a user'sfinancial data of another predetermined type is associated with a secondlogical region (e.g. 320, 330) on the touch screen display 305. At block430, a user selection of at least a portion of the user's financial datain each of the first and second logical regions is received. Anysuitable user selection method for selecting data in a first and secondlogical region, and associated logic for receiving a user selection ofthe data can be included in a system and method of executing atransaction request. In some embodiments, a user selection of at least aportion of the user's financial data in each of the first and secondlogical regions (320, 330) may be a drag and drop type of userselection. For example, in some embodiments, a system can include adevice 300 that can support an advanced markup language (e.g. HTML5,HTML4 with jQuery) including a Drag and Drop API (e.g. native Drag andDrop API). In some embodiments, objects associated with at least aportion of a user's financial data in two or more logical regions (e.g.310, 320, 330) and/or logical subregions (e.g. 312, 314, 316) areprogrammed to have draggable attributes to implement a Drag and Dropoperation with such objects. For example, a system can include logic toreceive a selection (e.g. a drag tap and hold, a drag click, a dragmouse click, etc.) of a portion of a user's financial data in onelogical region (e.g. a bill to be paid at 330, FIG. 3E) and execute aDrag and Drop event such that such user data portion is dragged overdisplay (305) and dropped over a portion of a user's financial data inanother logical region (e.g. accounts at 310, FIG. 3B) and/or logicalsubregion (e.g. checking account at 312, FIG. 3E) to associate (e.g.pair) the respective portions of the user's financial data in theselected logical regions and/or logical subregions.

In some embodiments, a user selection of at least a portion of theuser's financial data in each of the first and second logical regions(320, 330) may be a Long Touch, or a Long Press, or a Long Click, typeof user selection. For example, in some embodiments, a system caninclude a device 300 that can support a markup language (e.g. HTML5,HTML4 with jQuery) including a Long Touch API. In some embodiments,objects associated with at least a portion of a user's financial data intwo or more logical regions (e.g. 310, 320, 330) and/or logicalsubregions (e.g. 312, 314, 316) are programmed to have long touchattributes to implement a Long Touch operation (e.g. LongClick ( )) withsuch objects. For example, a system can include logic to receive aselection (e.g. a long touch, a long click, a long press, a focus of acursor over a portion with navigation-keys or a trackball and a longpress of an “enter” key or trackball, etc.) of a portion of a user'sfinancial data in one logical region (e.g. a bill to be paid at 330,FIG. 3E), receive another selection (e.g. a tap, a touch, a click, apress) of a portion of a user's financial data in another logical region(e.g. accounts at 310, FIG. 3B) and/or logical subregion (e.g. checkingaccount at 312, FIG. 3E), and execute a Long Touch event to associate(e.g. pair) the respective portions of the user's financial data in theselected logical regions and/or logical subregions. In some embodiments,a system can include logic to highlight the selected portion of a user'sfinancial data in a logical region and/or subregion to indicate when theLong Touch operation has been implemented for that logical region and/orsubregion. In other embodiments, a system can include logic to provide amovable image, for example a grayed movable image) of the selectedportion of a user's financial data in a logical region and/or subregionwhen the Long Touch operation has been implemented for that logicalregion and/or subregion.

In some embodiments, a user selection of at least a portion of theuser's financial data in each of the first and second logical regions(320, 330) may be a Multitouch type of user selection. For example, insome embodiments, a system can include a device 300 that can support amarkup language (e.g. HTML5, HTML4 with jQuery) including a MultitouchAPI. In some embodiments, objects associated with at least a portion ofa user's financial data in two or more logical regions (e.g. 310, 320,330) and/or logical subregions (e.g. 312, 314, 316) are programmed tohave multitouch attributes to implement a Multitouch operation with suchobjects. For example, a system can include logic to receive a selection(e.g. a touch, a tap, a click, a press, a touch and hold, a tap andhold, a click and hold, a press and hold, etc.) of a portion of a user'sfinancial data in one logical region (e.g. a bill to be paid at 330,FIG. 3E), receive another selection (e.g. a tap, a touch, a click, apress, etc.) of a portion of a user's financial data in another logicalregion (e.g. accounts at 310, FIG. 3B) and/or logical subregion (e.g.checking account at 312, FIG. 3E) while also receiving the selection ofthe portion of the user's financial data in the one logical region, andexecute a Multitouch event to associate (e.g. pair) the respectiveportions of the user's financial data in the selected logical regionsand/or logical subregions.

At block 440, the at least a portion of the user's financial data of thefirst logical region (e.g. 310) is associated with the at least aportion of the user's financial data of the second logical region (e.g.320, 330) based on the received user selection (e.g. Drag and Dropselection, Long Touch selection, Multitouch selection, etc.). Forexample, in embodiments including a Drag and Drop API, a system caninclude logic to associate a user's selected financial data in the firstlogical region with the user's selected financial data in the secondlogical region by, for example, including an instruction set toassociate the data set in code associated with the dragover (e.g.pairing) event. The inventor has determined that by providing anintelligent interface that minimizes navigational and hierarchical userinteractions with a financial transaction application or website cansignificantly improve a user's experience in initiating transactionrequests over the Internet. In some embodiments, an intelligentinterface where a user initiates a bill pay request by dragging a bill(e.g. FIG. 3E at 330) and dropping it over a checking account that theuser wishes to use for bill payment (e.g. FIG. 3E at 310) cansignificantly improve a user's web bill pay experience over hierarchicalmenu-driven bill payment systems.

In some embodiments, an intelligent interface where a user initiates anonline payment for items pre-added to a shopping cart by dragging ashopping cart and dropping it over a user's credit card account that theuser wishes to use for payment can significantly improve a user's onlineshopping experience over hierarchical menu-driven online paymentsystems. By way of example, an intelligent interface where a userinitiates an online download order for music pre-added to a musicdownloading site shopping cart by dragging a shopping cart and droppingit over a user's credit card account that the user wishes to use forpayment can significantly improve a user's online music downloadingexperience over hierarchical menu-driven online payment systems.

In some embodiments, a system includes logic to assign the at least aportion of the user's financial data of the logical region (e.g. 310),or logical subregion (e.g. 312), that is selected at an earlier point intime (e.g. dragged object, object that is long touched, object that istapped and held, etc.) as an initiating portion and logic to assign theat least a portion of the user's financial data of the logical region(e.g. 320, 330), or logical subregion (e.g. 314, 316), In someembodiments, a system can include logic to assign any portion of theuser's financial data of any logical region, or any logical subregion,that is selected at an earlier point in time as a default initiatingportion and logic to assign any portion of the user's financial data ofany logical region, or any logical subregion, that is selected at alater point in time as a default receiving portion. For example, atleast a portion of the user's account information in a first subregion(e.g. checking account information) can be assigned as a defaultinitiating portion when selected by a user at an earlier point in timeand at least a portion of the user's account information in a secondsubregion (e.g. savings account information) can be assigned as adefault receiving portion when selected by a user at a later point intime.

At block 450, a financial transaction is initiated based on the receiveduser selection and using the associated (e.g. paired) respectiveportions of the user's financial data of the first and second logicalregions (310, 320, 330). For example, in embodiments including a Dragand Drop API, a system can include logic to trigger initiation of afinancial transaction by, for example, including an instruction set toprovide a summary webpage including one or more transaction parametersassociated with the initiated transaction, or a confirmation webpage, atdisplay 305 including one or more transaction parameters to the user inresponse to the Drag and Drop event. In some embodiments, a method caninclude the step of displaying information associated with the initiatedfinancial transaction on the display 305 based on the received userselection and wherein the displayed information includes at least aportion of the associated respective portions of the user's financialdata of the first (e.g. 310) and second (e.g. 320, 330) logical regions.

In some embodiments, an initiating portion and a receiving portion canhave respective associated financial data loaded into predeterminedportions of a summary webpage, or a confirmation webpage, on the display305. For example, in embodiments including a Drag and Drop API,selecting a checking account portion of a logical subregion, draggingthe selected checking account portion over a savings account portion ofanother logical subregion, and dropping the selected checking accountportion over the selected savings account portion can have respectivechecking and savings account information associated (e.g. paired) andautomatically loaded into predetermined portions of a summary webpage,or a confirmation webpage, on the display 305 to initiate a fundstransfer transaction from the user's checking account to the user'ssavings account.

Referring now to FIG. 5A, an example of a screenshot according to someembodiments is provided. In the illustrated embodiment, a summarywebpage for an initiated Bill Payment is displayed on display 505 andcan include information associated with the initiated bill paymentrequest based on a received user selection (e.g. a Drag and Dropselection of a user's bill (e.g. FIG. 3E at 330) and a checking accountthat the user wishes to use for bill payment (e.g. FIG. 3E at 310)) andthe associated respective portions of the user's financial data of thefirst (e.g. 310) and second (e.g. 330) logical regions. In theillustrated embodiment, the displayed screenshot can include a name andaddress of a payee, a date due, a default data scheduled (e.g. the duedate on the bill), a default account to be debited (e.g. the selectedaccount of logic region 310), a default amount (e.g. the bill amount),etc.

In some embodiments, at least one selectable parameter for the initiatedfinancial transaction can be displayed at display 505 based on thereceived user selection and the associated respective portions of theuser's financial data of the first and second logical regions. As usedherein, a selectable parameter is a transaction parameter that can beselected and having a value that can be modified by the user. In theillustrated embodiment, the date scheduled 562 is a selectableparameter. The date scheduled selectable parameter 562 can be modifiedby a spin box 540, a text box for tactile entry by a user such as forexample, by a touch screen keyboard that is provided in response to auser selection of a text box or a keyboard that is part of a device(e.g. 300) or peripheral to the device (e.g. 300), or a calendar inlineimage 565 that can provide a touch screen calendar in response to a userselection of the calendar inline image 565. By way of example, in theillustrated embodiment, an account to be debited selectable parameter562 can be modified by spin box 540, and an amount to be paid selectableparameter that can be modified by a spin box 540, a text box for tactileentry by a user such as for example, by a touch screen keyboard that isprovided in response to a user selection of the text box or a keyboardthat is part of a device (e.g. 300) or peripheral to the device (e.g.300), or a numeric pad inline image 565 that can provide a touch screennumeric keypad in response to a user selection of the numeric pad inlineimage 565. In some embodiments, a selectable parameter can include, butis not limited to, an amount of the transaction, a date of thetransaction, an account associated with the transaction, a recurrencefor the transaction, a payee identifier, a payee address, a text box forinstructions associated with the transaction, a credit card associatedwith the transaction, a check associated with the transaction, and aconfirmation of information associated with the transaction.

In a system including logic to assign any portion of the user'sfinancial data of any logical region, or any logical subregion, that isselected at an earlier point in time as a default initiating portion andlogic to assign any portion of the user's financial data of any logicalregion, or any logical subregion, that is selected at a later point intime as a default receiving portion, a default financial transaction canautomatically be initiated. For example, in a system including logic toassign the at least a portion of the user's account information in afirst subregion (e.g. checking account information) as a defaultinitiating portion when selected by a user at an earlier point in timeand to assign the at least a portion of the user's account informationin a second subregion (e.g. savings account information) as a defaultreceiving portion when selected by a user at a later point in time, adefault funds transfer from the account associated with the firstsubregion into the account associated with the second subregion can beinitiated. By way of example, in a system including logic to assign theat least a portion of the user's future transaction information in afirst region (e.g. bill information) as a default initiating portionwhen selected by a user at an earlier point in time and to assign the atleast a portion of the user's account information in a second region(e.g. checking account information) as a default receiving portion whenselected by a user at a later point in time, a default bill payment ofthe bill associated with the first region from the account associatedwith the second region can be initiated.

In some embodiments, a system can include logic to evaluate or determinecompatibility or suitability of selected portions of a user's financialinformation in respective regions and/or subregions. In someembodiments, a system can include logic to evaluate or determinecompatibility of an assigned, selected default initiating portion and anassigned, selected default receiving portion prior to initiation of afinancial transaction. For example, a system can include logic toevaluate or determine whether the selected at least a portion of theuser's account information in a first subregion (e.g. savings accountinformation) is compatible with the selected at least a portion of theuser's account information in a second subregion (e.g. certificate ofdeposit account information) prior to initiation of a funds transfertransaction from the user's savings account to the user's certificate ofdeposit account. By way of example, a system can include logic toevaluate or determine whether the selected at least a portion of theuser's past transaction information in a first region (e.g. already paidbill information) is suitable for a transaction with the selected atleast a portion of the user's account information in a second region(e.g. checking account information) prior to initiation of a billpayment transaction from the user's checking account.

In some embodiments, a system can include logic to reject initiation ofa financial transaction if one or both of the respective selective userfinancial information portions are determined to be incompatible or notsuitable for a transaction. For example, a system can include logic todisplay a hover indicator (such as a circle with a slash or graying ofbackground) or an error message if a user attempts to select a portionof a region or subregion that is programmed as incompatible with anotherselected portion of another region or subregion or programmed as notsuitable for a financial transaction. In some embodiments, if logic toevaluate compatibility or suitability in a system determines that theselected at least a portion of a user's financial information in a firstregion or subregion is suitable for a transaction, and compatible withthe selected at least a portion of the user's financial information in asecond region or subregion, a financial transaction (e.g. a defaultfinancial transaction) can be initiated automatically.

Referring now to FIG. 6, a financial transaction can be initiated byperforming the steps at block blocks 610 to 650 as described above forblocks 410 to 450. At block 660, a user selection of at least oneselectable parameter is received. For example, as shown in FIG. 5A, auser selection (e.g. by touch entry input at touch screen display 305)of a date scheduled selectable parameter 562, an account to be debitedselectable parameter 562, an amount to be paid selectable parameter 562,a cancellation of a financial transaction request selectable parameter570, and/or a submission of a financial transaction request selectableparameter 575 can be received at block 660.

With reference to FIG. 5B, an example of a screenshot according to someembodiments is provided. In the illustrated embodiment, a confirmationwebpage for an initiated Bill Payment is displayed on display 505 andcan include information associated with the initiated bill paymentrequest based on a received user selection (e.g. a Drag and Dropselection of a user's bill (e.g. FIG. 3E at 330) and a checking accountthat the user wishes to use for bill payment (e.g. FIG. 3E at 310)) andthe associated respective portions of the user's financial data of thefirst (e.g. 310) and second (e.g. 330) logical regions. In someembodiments, a confirmation webpage can be provided based on a user'sselection of one or more selectable parameters 562. In anotherembodiment, a confirmation webpage can be provided and can include oneor more selectable parameters 562. In the illustrated embodiment, thedisplayed screenshot can include a simplified identification of thetransaction, a name of the payee, a date scheduled, an amount and anaccount to be debited displayed on display 505. In some embodiments, aconfirmation webpage can include an edit of a financial transactionrequest selectable parameter 580, a cancellation of a financialtransaction request selectable parameter 570, and/or a confirmation of afinancial transaction request selectable parameter 575. In someembodiments, the one or more selectable parameters illustrated in FIG.5B can be received at block 660. At block 670, the initiated financialtransaction can be executed based on the received user selection of theat least one selectable parameter.

The initiated financial transaction can be executed using any suitablemethod. For example, a financial institution or a third party serviceprovider (e.g. check service provider) can provide a paper check orelectronic check based on the customer's initiated financial transactionrequest (e.g. bill payment request) to the third party payee on behalfof the user. In an embodiment, the third party payee can then depositthe check in a financial institution of the third party, such as forexample, a bank of first deposit. One skilled in the art wouldunderstand that a bank of first deposit can include any financialinstitution where a customer's check is initially deposited to anaccount. For example, if the check is drawn on another financialinstitution or bank, the collecting bank may present the check directlyto a paying financial institution or the collecting bank may present thecheck to a correspondent bank or clearinghouse corporation, or to theFederal Reserve Bank for settlement against a paying financialinstitution's reserve account. One skilled in the art would alsounderstand that a Federal Reserve Bank may be any of the regional banksin the Federal Reserve System. In an embodiment, the bank of firstdeposit may scan the deposited check and send an electronic image of thedeposited check, or a substitute check, to a paying financialinstitution or Federal Reserve Bank as appropriate. In an embodimentincluding a Federal Reserve Bank, the Federal Reserve Bank may processthe check and send an electronic image, or substitute check, to thepaying bank through, for example, the Federal Reserve's AutomatedClearing House (ACH) system. In an embodiment, a correspondent bank orclearinghouse corporation may process the check through an electroniccheck processing system such as, for example, FedWire or Clearing HouseInterbank Payment System (CHIPS).

Referring now to FIG. 7, a method of executing a financial transactionrequest according to some embodiments is provided. At blocks 710 to 720,a plurality of a user's financial data of a respective predeterminedtype is associated with respective logical regions (310, 320, 33) on atouch screen display 305 as described above for blocks 410 to 420. Atblock 730, a first subset of the data of the first predetermined type isassociated with one logical subregion (e.g. 312) in one logical region(e.g. 310). For example, in some embodiments, account information of theuser (e.g. checking account information, a general services accountinformation, a savings account information, a mortgage accountinformation, a credit card account information, an investment accountinformation, a retirement account information, etc.) is associated withone logical subregion (e.g. 312) in one logical region (e.g. 310). Atblock 740, a second subset of the data of the first predetermined typeis associated with another logical subregion (314, 316) in the logicalregion (e.g. 310). For example, in some embodiments, other accountinformation of the user is associated with another logical subregion(314, 316) in the one logical region (e.g. 310). Referring back to FIG.3B, a user's checking account information can be associated with logicalsubregion 312 of logical region 310 and a user's savings accountinformation can be associated with logical subregion 314 of logicalregion 310. At block 750, a user selection of at least a portion of theuser's account information in each of the first (e.g. 312) and second(e.g. 314) logical subregions can be received. Any suitable userselection method can be used. For example, a user selection of at leasta portion of the user's financial data in each of the first and secondlogical subregions (e.g. 312, 314) can be a drag and drop type of userselection. In other embodiments, a user selection method can be a longtouch type of user selection or a multitouch type of user selection.

At block 760, the selected at least a portion of the data of one of theselected logical subregions (e.g. 312) can be associated (e.g. paired)with the selected at least a portion of the data of the other selectedlogical subregion (e.g. 314) based on the received user selection. Forexample, in some embodiments, a selected at least a portion of a user'saccount information of one of the selected logical subregions (e.g. 312)can be associated with the selected at least a portion of the user'saccount information of the other selected logical subregion (e.g. 314)based on the received user selection. For example, in embodimentsincluding a Drag and Drop API, a system can include logic to associate(e.g. pair) a user's selected financial data in the first logicalsubregion with the user's selected financial data in the second logicalsubregion by, for example, including an instruction set to associate thedata set in code associated with the dragover event. As described above,the inventor has determined that providing an intelligent interface thatminimizes navigational and hierarchical user interactions with afinancial transaction application or website can significantly improve auser's experience in initiating transaction requests over the Internet.In some embodiments, an intelligent interface where a user initiates afunds transfer request by dragging a checking account (e.g. FIG. 3B at312) and dropping it over a savings account that the user wishes totransfer funds into (e.g. FIG. 3B at 314) can significantly improve auser's web funds transfer experience over hierarchical menu-driven fundstransfer systems. In some embodiments, an intelligent interface where auser initiates an online funds transfer request by dragging a checkingaccount (e.g. FIG. 3B at 312) and dropping it over a credit card accountthat the user wishes to transfer funds into (e.g. FIG. 3B at 316) cansignificantly improve a user's web credit card payment experience overhierarchical menu-driven credit card payment systems.

At block 770, a financial transaction can be initiated based on thereceived user selection and using the associated respective selectedportions of the data of the first (e.g. 312) and second (e.g. 314, 316)logical subregions. For example, in some embodiments, a funds transferfinancial transaction between a user's accounts can be initiated basedon the received user selection and using the associated respectiveselected portions of the user's account information of the first (e.g.312) and second (e.g. 314, 316) logical subregions. For example, inembodiments including a Drag and Drop API, a system can include logic totrigger initiation of a financial transaction by, for example, includingan instruction set to provide a summary webpage including one or moretransaction parameters associated with the initiated transaction, or aconfirmation webpage, at display 305 including one or more transactionparameters to the user in response to the Drag and Drop event. In someembodiments, a method can include the step of displaying informationassociated with the initiated financial transaction on the display 305based on the received user selection and wherein the displayedinformation includes at least a portion of the associated respectiveportions of the user's financial data of the first (e.g. 312) and second(e.g. 314, 316) logical subregions. In some embodiments, in a systemincluding logic to assign the first subset of user financial data of afirst predetermined type (e.g. checking account information) as adefault initiating portion when selected by a user at an earlier pointin time and to assign the second subset of user financial data of thefirst predetermined type (e.g. savings account information) as a defaultreceiving portion when selected by the user at a later point in time,the system can automatically initiate a default funds transfer from theaccount associated with the first subregion into the account associatedwith the second subregion. In some embodiments, a system can determinethe compatibility of the selected initiating portion and receivingportions of user financial data, and/or determine whether the selectedinitiating portion is suitable for a default transaction with theselected receiving portion, prior to initiation of the default financialtransaction. In some embodiments, a system can reject initiation of adefault financial transaction if one or both of the selected initiatingand receiving portions of user financial data are determined to beincompatible or not suitable for the default financial transaction.

Referring now to FIG. 8A, an example of a screenshot according to someembodiments is provided. In the illustrated embodiment, a summarywebpage for an initiated funds transfer transaction is displayed ondisplay 805 and can include information associated with the initiatedfunds transfer request based on a received user selection (e.g. a Dragand Drop selection of a user's checking account (e.g. FIG. 3B at 312)and a user's savings account that the user wishes to transfer funds into(e.g. FIG. 3B at 314)) and the associated respective portions of theuser's financial data of the first (e.g. 312) and second (e.g. 314)logical subregions. In the illustrated embodiment, the displayedscreenshot can include a checking account number, a bank holding thechecking account, a savings account number, a bank holding the savingsaccount, last funds transfer information between the two accounts, adefault transfer amount, default data scheduled (e.g. a date that thefunds transfer request was initiated), etc.

In some embodiments, at least one selectable parameter for the initiatedfinancial transaction can be displayed at display 805 based on thereceived user selection and the associated respective portions of theuser's financial data of the first (e.g. 312) and second (e.g. 314, 316)logical subregions. In the illustrated embodiment, the transfer datescheduled 862 is a selectable parameter. The transfer date scheduledselectable parameter 862 can be modified by a spin box 840, a text box,a calendar inline image 865, etc. By way of example, in the illustratedembodiment, a repeat transfer selectable parameter 862 can be providedto permit a user to repeat a prior funds transfer between the selectedaccounts. A transfer amount selectable parameter 862 can be selected by,for example, a selection of one of the inline image transfer amounts.Referring now to FIG. 9, a financial transaction can be initiated byperforming the steps at blocks 910 to 970 as described above for blocks710 to 770. At block 980, a user selection of at least one selectableparameter is received. For example, as shown in FIG. 8A, a userselection (e.g. by touch entry input at touch screen display 805) of adate scheduled selectable parameter 862, a repeat transfer selectableparameter 862, a transfer amount selectable parameter 862, acancellation of a financial transaction request selectable parameter870, and/or a submission of a financial transaction request selectableparameter 875 can be received at block 880.

With reference to FIG. 8B, an example of a screenshot according to someembodiments is provided. In the illustrated embodiment, a confirmationwebpage for an initiated funds transfer is displayed on display 805 andcan include information associated with the initiated funds transferrequest based on a received user selection (e.g. a Drag and Dropselection of a user's checking account (e.g. FIG. 3B at 312) and asavings account that the user wishes to transfer funds into (e.g. FIG.3B at 314)) and the associated respective portions of the user'sfinancial data of the first (e.g. 312) and second (e.g. 314) logicalsubregions. In some embodiments, a confirmation webpage can be providedbased on a user's selection of one or more selectable parameters 862. Inanother embodiment, a confirmation webpage can be provided and caninclude one or more selectable parameters 862. In the illustratedembodiment, the displayed screenshot can include a simplifiedidentification of the transaction, an identification of the recipientaccount, an identification of the financial institution of the recipientaccount, a transfer amount and an identification of the transferoraccount. In some embodiments, a confirmation webpage can include an editof a financial transaction request selectable parameter 880, acancellation of a financial transaction request selectable parameter870, and/or a confirmation of a financial transaction request selectableparameter 875. In some embodiments, the one or more selectableparameters illustrated in FIG. 8B can be received at block 880. At block890, the initiated financial transaction can be executed based on thereceived user selection of the at least one selectable parameter. Theinitiated financial transaction can be executed using any suitablemethod.

Referring now to FIG. 10, a simplified block diagram is providedaccording to an embodiment of the present disclosure. At blocks 1010 to1020, a plurality of a user's financial data of a respectivepredetermined type is associated with respective logical regions (310,320, 330) on a touch screen display 305 as described above for blocks410 to 420. At block 1030, a plurality of a user's financial data of apredetermined type is associated with another logical region (e.g. 310,320, 330). At block 1040, a user selection of data in one logical region(e.g. 320) is received. For example, a user selection of a past billpaid (e.g. FIG. 3B at 320) in one logical region can be received. Anysuitable user selection method can be used. In another embodiment, auser selection of a future bill scheduled to be paid can be received. Atblock 1050, a financial transaction request can be initiated. Forexample, a dispute of a past bill paid or other financial transactioncan be initiated at block 1050. In another embodiment, a cancellationrequest of a scheduled bill payment or other financial transaction canbe initiated at block 1050.

In some embodiments, a method can include the step of displayinginformation associated with the initiated financial transaction on thedisplay 1105 based on the received user selection and wherein thedisplayed information includes at least a portion of the associatedportion of the user's financial data of the selected logical region(e.g. 320). Referring now to FIG. 11A, an example of a screenshotaccording to some embodiments is provided. In the illustratedembodiment, a cancellation webpage for a scheduled bill paymenttransaction is displayed on display 1105 and can include informationassociated with the initiated bill payment cancellation based on areceived user selection (e.g. a tap or click of a bill scheduled forpayment (e.g. FIG. 3B at 330) and the associated portion of the user'sfinancial data of the third (e.g. 330) logical region. In theillustrated embodiment, the displayed screenshot can include adescription of the bill payment, the payee, the account number to bedebited, and the scheduled payment amount. In the illustratedembodiment, a cancellation webpage can include an edit of a dateselectable parameter 1162, an edit of an amount selectable parameter1162, an edit of an account selectable parameter 1162, a cancellation ofa financial transaction request selectable parameter 1170, and/or anysuitable selectable parameter 1162.

Referring now to the embodiment illustrated in FIG. 11B, a summarywebpage for a disputed financial transaction is displayed on display1105 and can include information associated with the initiated financialtransaction dispute based on a received user selection (e.g. a tap orclick of a past financial transaction (e.g. FIG. 3B at 320) and theassociated portion of the user's financial data of the second (e.g. 320)logical region. In the illustrated embodiment, the displayed screenshotcan include a description of past transaction, the payee, the payeeaddress, the account number (or card number) for the account debited,the transaction date and the transaction amount. In the illustratedembodiment, a dispute webpage can include a text box selectableparameter 1162, a submission of a financial transaction dispute requestselectable parameter 1170, or any suitable selectable parameter 1162. Insome embodiments, the one or more selectable parameters illustrated inFIGS. 11A and 11B can be received at block 1050. The initiated financialtransaction can be executed based on the received user selection of theat least one selectable parameter. The initiated financial transactioncan be executed using any suitable method.

While portions of this disclosure have been described with reference toa financial institution, this should not limit the scope of the claimsappended herewith, as the present subject matter may find utility inmany different instances where it is necessary to interface withfinancial information or execute a financial transaction request.

The present disclosure may be implemented by a general purpose computeror server programmed in accordance with the principals discussed herein.It may be emphasized that the above-described embodiments, particularlyany “preferred” embodiments, are merely possible examples ofimplementations, merely set forth for a clear understanding of theprinciples of the disclosure. Many variations and modifications may bemade to the above-described embodiments of the disclosure withoutdeparting substantially from the spirit and principles of thedisclosure. All such modifications and variations are intended to beincluded herein within the scope of this disclosure and the presentdisclosure and protected by the following claims.

Embodiments of the subject matter and the functional operationsdescribed in this specification may be implemented in digital electroniccircuitry, or in computer software, firmware, or hardware, including thestructures disclosed in this specification and their structuralequivalents, or in combinations of one or more of them. Embodiments ofthe subject matter described in this specification may be implemented asone or more computer program products, i.e., one or more modules ofcomputer program instructions encoded on a transitory or non-transitory,tangible program carrier for execution by, or to control the operationof, a data processing apparatus. The non-transitory, tangible programcarrier may be a computer readable storage medium. As discussed above,the computer readable storage medium may be a machine-readable storagedevice, a machine-readable storage substrate, a memory device, or acombination of one or more of them.

The term “processor” encompasses all apparatus, devices, and machinesfor processing data, including by way of example a programmableprocessor, a computer, server, or multiple processors, computers orservers. These apparatus, devices and machines may include (in additionto hardware) code that creates an execution environment for the computerprogram in question, e.g., code that constitutes processor firmware, aprotocol stack, a database management system, an operating system, or acombination of one or more of them.

A computer program (also known as a program, software, softwareapplication, script, or code) may be written in any form of programminglanguage, including compiled or interpreted languages, or declarative orprocedural languages, and it may be deployed in any form, including as astandalone program or as a module, component, subroutine, or other unitsuitable for use in a computing environment. A computer program does notnecessarily correspond to a file in a file system. A program may bestored in a portion of a file that holds other programs or data (e.g.,one or more scripts stored in a markup language document), in a singlefile dedicated to the program in question, or in multiple coordinatedfiles (e.g., files that store one or more modules, sub programs, orportions of code). A computer program may be deployed to be executed onone computer or on multiple computers that are located at one site ordistributed across multiple sites and interconnected by a communicationnetwork.

The processes and logic flows described in this specification may beperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating output. The processes and logic flows may also be performedby and/or implemented as special purpose logic circuitry, e.g., a fieldprogrammable gate array (FPGA) or an application specific integratedcircuit (ASIC). These processors and/or circuitry may be resident on anexemplary device described above or on servers in an exemplary bankingsystem.

For example, and referring now to FIG. 12, a block diagram of aprocessing system according to an embodiment of the present disclosureis provided. For example, FIG. 12 shows a processor 1202 programmed toperform the method steps. The steps can be performed by a plurality ofseparate computer programs, or by a program that prompts the user foradditional inputs between and/or during steps. These steps can includeone or more of the associating user financial data with each logicalregion on the display 1211, varying an amount of financial datadisplayed in logical regions of the display 1212, varying financial datadisplayed logical regions on the display 1213, associating userfinancial data with each subregion in a logical region of the display1214, varying an amount of financial data displayed in logicalsubregions of the display 1215, varying financial data displayed inlogical subregions on the display 1216, initiating financial transaction1217; displaying information associated with initiated financialtransaction 1218, displaying selectable parameters for initiatedfinancial transaction 1219, execute initiated financial transaction1220, edit initiated financial transaction 1221, modify scheduledfinancial transactions 1222, dispute past financial transactions 1223,associating data between logical regions of the display 1224, andassociating data between logical subregions of the display 1225. In someembodiments, these steps can include one or more of the assigning aselected portion as an initiating portion, assigning a selected portionas a receiving portion, evaluating whether selected portions arecompatible, evaluating whether selected portions are suitable for atransaction, rejecting an initiated financial transaction, andinitiating a financial transaction automatically. As shown in FIG. 12,user input types 1230-1233 can be received by programmed processor 1202.In some embodiments, all numerically intensive calculations areperformed by a programmed processor. Although FIG. 12 shows a singleprocessor, in other embodiments, various subsets of the processes1211-1225 can be executed on a plurality of programmed processors, whichcan optionally be connected to each other by a communications network,such as a personal area network, a local area network, a wide areanetwork, and/or the Internet.

Processors suitable for the execution of a computer program include, byway of example, both general and special purpose microprocessors, andany one or more processors of any kind of digital computer. Generally, aprocessor will receive instructions and data from a read only memory ora random access memory or both. While the essential elements of acomputer are a processor for performing instructions and one or moredata memory devices for storing instructions and data, a computer mayalso include, or be operatively coupled to receive data from or transferdata to, or both, one or more mass storage devices for storing data,e.g., magnetic, magneto optical disks, or optical disks. However, acomputer need not have such devices. Moreover, a computer may beembedded in another device, e.g., a tablet, a smart phone, a mobiletelephone, a personal digital assistant (PDA), a mobile audio or videoplayer, a game console, to name just a few.

Computer readable storage media suitable for storing computer programinstructions and data include all forms data memory includingnon-volatile memory, media and memory devices, including by way ofexample semiconductor memory devices, e.g., EPROM, EEPROM, and flashmemory devices; magnetic disks, e.g., internal hard disks or removabledisks; magneto optical disks; and CD ROM and DVD-ROM disks. Theprocessor and the memory may be supplemented by, or incorporated in,special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described in this specification may be implemented on a computerhaving a display device, e.g., a cathode ray tube (CRT) or liquidcrystal display (LCD) monitor, for displaying information to the userand a touch screen and a keyboard and a pointing device, e.g., a mouseor a trackball, by which the user may provide input to the computer.Other kinds of devices may be used to provide for interaction with auser as well; for example, input from the user may be received in anyform, including acoustic, speech, or tactile input.

As discussed above, embodiments of the subject matter described in thisspecification may be implemented in a computing system that includes aback end component, e.g., as a data server, or that includes amiddleware component, e.g., an application server, or that includes afront end component, e.g., a client computer having a graphical userinterface or a Web browser through which a user may interact with animplementation of the subject matter described is this specification, orany combination of one or more such back end, middleware, or front endcomponents. The components of the system may be interconnected by anyform or medium of digital data communication, e.g., a communicationnetwork. Examples of communication networks include a local area network(LAN) and a wide area network (WAN), e.g., the Internet. The computingsystem may include clients and servers. A client and server aregenerally remote from each other and typically interact through acommunication network. The relationship of client and server arises byvirtue of computer programs running on the respective computers andhaving a client-server relationship to each other.

While this specification contains many specifics, these should not beconstrued as limitations on the scope of the claimed subject matter, butrather as descriptions of features that may be specific to particularembodiments. Certain features that are described in this specificationin the context of separate embodiments may also be implemented incombination in a single embodiment. Conversely, various features thatare described in the context of a single embodiment may also beimplemented in multiple embodiments separately or in any suitablesubcombination. Moreover, although features may be described above asacting in certain combinations and even initially claimed as such, oneor more features from a claimed combination may in some cases be excisedfrom the combination, and the claimed combination may be directed to asubcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in sequential order, orthat all illustrated operations be performed, to achieve desirableresults. In certain circumstances, multitasking and parallel processingmay be advantageous. Moreover, the separation of various systemcomponents in the embodiments described above should not be understoodas requiring such separation in all embodiments, and it should beunderstood that the described program components and systems maygenerally be integrated together in a single software product orpackaged into multiple software products.

As shown by the various configurations and embodiments illustrated inFIGS. 1-12, a system and method for interfacing with financialinformation have been described.

While preferred embodiments of the present subject matter have beendescribed, it is to be understood that the embodiments described areillustrative only and that the scope of the invention is to be definedsolely by the appended claims when accorded a full range of equivalence,many variations and modifications naturally occurring to those of skillin the art from a perusal hereof.

What I claim is:
 1. A method of configuring an interactive userinterface for intuitively executing a financial transaction request viaa mobile computing device, the method comprising: transmitting, to themobile computing device, the user interface for display on atouch-screen display of the mobile computing device, the user interfaceincluding: a first logical region having first predetermined boundaries,the first logical region being associated with one or more financialaccounts associated with a user and being configured to display,responsive to receiving user input corresponding to the first logicalregion, one or more account subregions, each of the one or more accountsubregions disposed within the first logical region and associated witha corresponding financial account of the one or more financial accounts;and a second logical region having second predetermined boundaries, thesecond logical region non-overlapping with respect to the first logicalregion and being associated with transactional information of the useraccount and being configured to transition, responsive to receiving userinput corresponding to the second logical region, between displaying afirst level of transactional data having a first granularity and asecond level of transaction data having a second granularity that isgreater than the first granularity, the second level of transaction datacomprising a plurality of transactional subregions, each of thetransactional subregions being associated with a corresponding futuretransaction; receiving, via the user interface, a multi-part selectionincluding: a first touch input associated with selection of an accountsubregion of the one or more account subregions; and a second touchinput associated with selection of a transactional subregion of theplurality of transactional subregions, each of the first and secondtouch inputs including a drag and drop selection, long touch selection,and/or multitouch selection; and responsive to determining that thereceived multi-part selection is indicative of the financial transactionrequest, initiating, via a processor, a financial transaction from thefinancial account associated with the selected account subregion and forthe future transaction associated with the selected transactionalsubregion.
 2. The method of claim 1, further comprising: displayinginformation associated with the initiated financial transaction on thetouch-screen display based on the received multi-part selection, whereinthe displayed information includes data associated with the financialaccount associated with the selected account subregion and the futuretransaction associated with the selected transactional subregion.
 3. Themethod of claim 1, further comprising: displaying at least oneselectable parameter for the initiated financial transaction based onthe received multi-part selection, the selected account subregion, andfuture transaction associated with the selected transactional subregion.4. The method of claim 3, wherein the at least one selectable parameteris selected from the group consisting of an amount of the transaction, adate of the transaction, an account associated with the transaction, arecurrence for the transaction, a payee identifier, a payee address, atext box for instructions associated with the transaction, a credit cardassociated with the transaction, a check associated with thetransaction, and a confirmation of information associated with thetransaction.
 5. The method of claim 3, further comprising: receiving aselection of the at least one selectable parameter; and executing, viathe processor, the initiated financial transaction based on the receivedselection of the at least one selectable parameter.
 6. The method ofclaim 1, wherein the transactional information comprises at least one ofa bill from a payee, a stock, an exchange-traded fund, a money transfer,a deposit, a mortgage, an order, a scheduled payment, a savings plan,and an investment plan.
 7. The method of claim 1, further comprising:determining, by the processor, whether the selected account subregionand the selected transactional subregion are compatible; responsive todetermining that the selected account subregion and the selectedtransactional subregion are compatible, initiating, by the processor,the financial transaction; and responsive to determining that theselected account subregion and the selected transactional subregion areincompatible, rejecting, by the processor, initiation of the financialtransaction.
 8. The method of claim 1, further comprising: determining,by the processor, whether the selected account subregion and theselected transactional subregion are suitable for the financialtransaction; responsive to determining that the selected accountsubregion and the selected transactional subregion are suitable for thefinancial transaction, initiating, by the processor, the financialtransaction; and responsive to determining that the selected accountsubregion and the selected transactional subregion are unsuitable forthe financial transaction, rejecting, by the processor, initiation ofthe financial transaction.
 9. The method of claim 1 further comprising:prior to initiating the financial transaction, requesting, by theprocessor, confirmation that the received multi-part selection isindicative of a request for the financial transaction.
 10. The method ofclaim 1 further comprising: associating past transactional informationof the user with a third logical region having third predeterminedboundaries on the touch screen display, wherein the respectivepredetermined boundaries of the first, second, and third logical regionsdo not overlap with each other.
 11. The method of claim 1, wherein therespective predetermined boundaries of the first and second logicalregions are expandable.
 12. The method of claim 1, wherein a type ofuser input comprises an open pinch being associated with more specificinformation and a closed pinch being associated with more generalinformation.
 13. A method of configuring an interactive user interfacefor intuitively executing a financial transaction request via a mobilecomputing device, the method comprising: transmitting, to the mobilecomputing device, the user interface for display on a touch-screendisplay of the mobile computing device, the interface including: a firstlogical region having first predetermined boundaries, the first logicalregion being associated with account information of a user account andbeing configured to expand, responsive to receiving user inputcorresponding to the first logical region, to display an increasedportion of the account information; a second logical region havingsecond predetermined boundaries, the second logical regionnon-overlapping with respect to the first logical region and beingassociated with transactional information of the user account and beingconfigured to expand, responsive to receiving user input correspondingto the second logical region, to display an increased portion of thetransactional information; a first logical subregion having thirdpredetermined boundaries within the first logical region, the firstlogical subregion being associated with a first subset of the increasedportion of the account information; and a second logical subregionhaving fourth predetermined boundaries within the first logical region,the second logical subregion being associated with a second subset ofthe increased portion of the account information; receiving a multi-partselection including: receiving, via the user interface, input associatedwith selection of a portion of the account information in each of thefirst and second logical subregions, the input including a drag and dropselection, long touch selection, and/or multitouch selection; andresponsive to determining that the received multi-part selection isindicative of the financial transaction request, initiating, via aprocessor, a financial transaction corresponding to data associated withthe first logical subregion and the second logical subregion.
 14. Themethod of claim 13, further comprising: displaying informationassociated with the initiated financial transaction on the touch-screendisplay based on the received multi-part selection, wherein thedisplayed information includes data associated with the first and secondlogical subregions.
 15. The method of claim 13, further comprising:displaying at least one selectable parameter for the initiated financialtransaction based on the received multi-part selection, the firstlogical subregion, and the second logical subregion.
 16. The method ofclaim 15, wherein the at least one selectable parameter is selected fromthe group consisting of an amount of the transaction, a date of thetransaction, a recurrence for the transaction, a text box forinstructions associated with the transaction, and a confirmation ofinformation associated with the transaction.
 17. The method of claim 15,further comprising: receiving a user's selection of the at least oneselectable parameter; and executing, via the processor, the initiatedfinancial transaction based on the received selection of the at leastone selectable parameter.
 18. The method of claim 13, wherein therespective account information of the respective first and secondlogical subregions comprises at least one of checking accountinformation, savings account information, mortgage account information,brokerage account information, credit card account information,investment account information, certificate of deposit accountinformation and retirement account information.
 19. The method of claim13, further comprising: determining, by the processor, whether theselected portion of the account information in the first logicalsubregion and the selected portion of the account information in thesecond logical subregion are compatible; responsive to determining thatthe selected portion of the account information in the first logicalsubregion and the selected portion of the account information in thesecond logical subregion are compatible, initiating, by the processor,the financial transaction; and responsive to determining that theselected portion of the account information in the first logicalsubregion and the selected portion of the account information in thesecond logical subregion are incompatible, rejecting, by the processor,initiation of the financial transaction.
 20. The method of claim 13,further comprising: determining, by the processor, whether the selectedportion of the account information in the first logical subregion andthe selected portion of the account information in the second logicalsubregion are suitable for the financial transaction; responsive todetermining that the selected portion of the account information in thefirst logical subregion and the selected portion of the accountinformation in the second logical subregion are suitable for thefinancial transaction, initiating, by the processor, the financialtransaction; and responsive to determining that the selected portion ofthe account information in the first logical subregion and the selectedportion of the account information in the second logical subregion aresuitable for the financial transaction, rejecting, by the processor,initiation of the financial transaction.
 21. The method of claim 13,wherein the selected portion of the account information in the firstlogical subregion comprises all account information displayed in thefirst logical region.
 22. The method of claim 13, wherein the selectedportion of the transactional information in the second logical subregioncomprises all transactional information displayed in the second logicalregion.
 23. The method of claim 13, wherein the account information ofthe first logical region is expandable, based on a type of user inputvia the touch screen, between more general account information and morespecific account information, and wherein the transactional informationof the second logical region is expandable, based on a type of userinput via the touch screen, between more general transactionalinformation and more specific transaction information.
 24. The method ofclaim 23, wherein the type of user input comprises an open pinch beingassociated with more specific information and a closed pinch beingassociated with more general information.